System and method for processing financial transactions using a mobile device for payment

ABSTRACT

A method for processing a financial transaction includes: storing, in a database, a plurality of wallet data entries, wherein each wallet data entry includes at least a mobile device identifier and payment details associated with at least one payment account; receiving, by a receiving device, an authorization request for a financial transaction, wherein the authorization request includes at least a mobile device identifier and transaction data; transmitting, to a mobile computing device associated with the mobile device identifier, at least the transaction data; receiving, from the mobile computing device, an indication of a payment account for funding of the financial transaction; identifying, in the database, payment details associated with the indicated payment account in a wallet data entry including the mobile device identifier included in the authorization request; and transmitting, to an issuer associated with the indicated payment account, at least the payment details and the transaction data.

FIELD

The present disclosure relates to the conducting of financialtransactions using a mobile device, specifically the selection of apayment account for funding a financial transaction using a mobiledevice for Internet and point-of-sale transactions.

BACKGROUND

The use of mobile devices to conduct payment transactions via near fieldcommunication has been beneficial for both consumers and merchants.Consumers may be able to conduct financial transactions using theirmobile device without the need to carry a physical payment card, whichmay result in higher account security. However, some mobile devices maynot be configured to securely store payment credentials, which may makethem unable to be used to conduct financial transactions. Furthermore,many consumers may be apprehensive to use their mobile devices for fearof their payment account information being intercepted via the nearfield communication process.

Thus, there is a need for a technical solution to providing a platformfor consumers to use a mobile device to conduct financial transactions,without the need for payment credentials to be stored locally on themobile device or transmitted to or from the mobile device. Such asolution may enable a consumer to engage in financial transactions bothon the Internet and at a point-of-sale, without the need for theconsumer to exchange or possess account information. This may result inadditional security and peace of mind for the consumer, which may resultin increased business activity for merchants.

SUMMARY

The present disclosure provides a description of systems and methods forthe processing of financial transactions and identification of paymentdetails.

A method for processing a financial transaction includes: storing, in adatabase, a plurality of wallet data entries, wherein each wallet dataentry includes at least a mobile device identifier and payment detailsassociated with at least one payment account; receiving, by a receivingdevice, an authorization request for a financial transaction, whereinthe authorization request includes at least a mobile device identifierand transaction data; transmitting, to a mobile computing deviceassociated with the mobile device identifier, at least the transactiondata; receiving, from the mobile computing device, an indication of apayment account for funding of the financial transaction; identifying,in the database, payment details associated with the indicated paymentaccount in a wallet data entry including the mobile device identifierincluded in the authorization request; and transmitting, to an issuerassociated with the indicated payment account, at least the paymentdetails and the transaction data.

A method for identifying payment details includes: storing, in adatabase, a plurality of wallet data entries, wherein each wallet dataentry includes at least a mobile device identifier and payment detailsassociated with at least one payment account; receiving, by a receivingdevice, a payment information request, wherein the payment informationrequest includes a mobile device identifier; transmitting, to a mobilecomputing device associated with the mobile device identifier, aselection request; receiving, from the mobile computing device, anindication of a payment account in response to the transmittingselection request; identifying, in the database, a specific wallet dataentry including the mobile device identifier included in the paymentinformation request; identifying, in the specific wallet data entry,payment details associated with the indicated payment account; andtransmitting, by a transmitting device, the identified payment details.

A system for processing a financial transaction includes a processingdevice, a database, a receiving device, and a transmitting device. Thedatabase is configured to store a plurality of wallet data entries,wherein each wallet data entry includes at least a mobile deviceidentifier and payment details associated with at least one paymentaccount. The receiving device is configured to receive an authorizationrequest for a financial transaction, wherein the authorization requestincludes at least a mobile device identifier and transaction data. Thetransmitting device is configured to transmit, to a mobile computingdevice associated with the mobile device identifier, at least thetransaction data. The receiving device is further configured to receive,from the mobile computing device, an indication of a payment account forfunding of the financial transaction. The processing device isconfigured to identify, in the database, payment details associated withthe indicated payment account in a wallet data entry including themobile device identifier included in the authorization request. Thetransmitting device is further configured to transmit, to an issuerassociated with the indicated payment account, at least the paymentdetails and the transaction data.

A system for identifying payment details includes a processing device, adatabase, a receiving device, and a transmitting device. The database isconfigured to store a plurality of wallet data entries, wherein eachwallet data entry includes at least a mobile device identifier andpayment details associated with at least one payment account. Thereceiving device is configured to receive a payment information request,wherein the payment information request includes a mobile deviceidentifier. The transmitting device is configured to transmit, to amobile computing device associated with the mobile device identifier, aselection request. The receiving device is further configured toreceive, from the mobile computing device, an indication of a paymentaccount in response to the transmitting selection request. Theprocessing device is configured to identify, in the database, a specificwallet data entry including the mobile device identifier included in thepayment information request, and identify, in the specific wallet dataentry, payment details associated with the indicated payment account.The transmitting device is further configured to transmit the identifiedpayment details.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The scope of the present disclosure is best understood from thefollowing detailed description of exemplary embodiments when read inconjunction with the accompanying drawings. Included in the drawings arethe following figures:

FIG. 1 is a high level architecture illustrating a system for theprocessing of financial transactions and transmitting of payment detailsbased on indications received from a mobile device in accordance withexemplary embodiments.

FIG. 2 is a block diagram illustrating the processing server of FIG. 1for the processing of financial transactions in accordance withexemplary embodiments.

FIGS. 3A and 3B are a process flow illustrating a method for conductinga financial transaction using the mobile device and processing server ofFIG. 1 in accordance with exemplary embodiments.

FIG. 4 is a flow chart illustrating methods for processing financialtransactions and transmitting payment details in accordance withexemplary embodiments.

FIGS. 5A-5F are illustrations of a graphical user interface forconducting an Internet financial transaction using the mobile device ofFIG. 1 in accordance with exemplary embodiments.

FIG. 6 is a flow chart illustrating an exemplary method for processing afinancial transaction in accordance with exemplary embodiments.

FIG. 7 is a flow chart illustrating an exemplary method for identifyingpayment details in accordance with exemplary embodiments.

FIG. 8 is a block diagram illustrating a computer system architecture inaccordance with exemplary embodiments.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description of exemplary embodiments areintended for illustration purposes only and are, therefore, not intendedto necessarily limit the scope of the disclosure.

DETAILED DESCRIPTION Definition of Terms

Payment Network—A system or network used for the transfer of money viathe use of cash-substitutes. Payment networks may use a variety ofdifferent protocols and procedures in order to process the transfer ofmoney for various types of transactions. Transactions that may beperformed via a payment network may include product or servicepurchases, credit purchases, debit transactions, fund transfers, accountwithdrawals, etc. Payment networks may be configured to performtransactions via cash-substitutes, which may include payment cards,letters of credit, checks, financial accounts, etc. Examples of networksor systems configured to perform as payment networks include thoseoperated by MasterCard®, VISA®, Discover®, American Express®, etc.

Payment Account—A financial account that may be used to fund atransaction, such as a checking account, savings account, creditaccount, virtual payment account, etc. A payment account may beassociated with an entity, which may include a person, family, company,corporation, governmental entity, etc. In some instances, a paymentaccount may be virtual, such as those accounts operated by PayPal®, etc.

Payment Card—A card or data associated with a payment account that maybe provided to a merchant in order to fund a financial transaction viathe associated payment account. Payment cards may include credit cards,debit cards, charge cards, stored-value cards, prepaid cards, fleetcards, virtual payment numbers, virtual card numbers, controlled paymentnumbers, etc. A payment card may be a physical card that may be providedto a merchant, or may be data representing the associated paymentaccount (e.g., as stored in a communication device, such as a smartphone or computer). For example, in some instances, data including apayment account number may be considered a payment card for theprocessing of a transaction funded by the associated payment account. Insome instances, a check may be considered a payment card whereapplicable. Payment cards may also include real card accounts havingassociated real card account numbers (RCAs) and mobile cloud accountshaving associated mobile cloud account numbers (MCAs) as discussed inmore detail herein.

System for Processing Financial Transactions Conducting with a MobileDevice

FIG. 1 illustrates a system 100 for processing financial transactionsconducted with a mobile device and the identification of payment detailsas indicated by a mobile device.

A consumer 102 may have one or more payment accounts (e.g., payment cardaccounts) issued by an issuer 104, such as an issuing bank. It is notedthat as used herein a consumer 102 does not have to consume or purchaseproducts or services, but rather be anyone or any entity desiring totransfer money to another person or entity. The consumer 102 may have amobile device 106. The mobile device 106 may be any type of mobilecomputing device suitable for performing the functions as disclosedherein, such as a cellular phone, smart phone, NFC-enabled phone, tabletcomputer, etc. Suitable configurations of the mobile device 106 will beapparent to persons having skill in the relevant art, such as thecomputer system 800 illustrated in FIG. 8 and discussed in more detailbelow.

The mobile device 106 may include payment selection data 108. Thepayment selection data 108 may include data suitable for the selectionof a payment account associated with the consumer 102 for use in fundinga financial transaction. In an exemplary embodiment, the paymentselection data 108 may not include any personally identifiableinformation or information that may compromise the associated paymentaccounts, such as payment account numbers. For example, the paymentselection data 108 may include the last four digits of the associatedpayment account number and a nickname associated with the paymentaccount.

The consumer 102 may initiate a financial transaction with a merchant112 for the purchase of products (e.g., goods and/or services). Itshould be noted that as used herein the merchant 112 can be a person ina person-to-person (P2P) payment transaction, a pre-paid card provider(thereby enabling a top-up or increases in the remaining value on thepre-paid card), a utility to enable utility payments, data and voiceservice provider enabling purchase of additional air time or increasinga data plan, etc., and virtually any other entity that wishes to receivepayments with the involvement of a mobile device 106 of a consumer 102.In some embodiments, the consumer 102 may initiate an in-personfinancial transaction, such as conducted at a physical location of themerchant 112 via a point-of-sale terminal. In other embodiments, theconsumer 102 may initiate the financial transaction via a network 120,such as the Internet. In some instances, the Internet transaction may beconducted with the mobile device 106 via a mobile network operator 110(e.g., a wireless service provider). In other instances, the Internettransaction may be conducted with a separate device, such as a computingdevice (e.g., desktop computer, laptop computer, notebook computer,etc.).

The merchant 112 may enter transaction details into a transaction system(e.g., via the point-of-sale terminal or through an Internet webpage).The merchant 112 may then prompt the consumer 102 to provide paymentdetails for funding of the financial transaction. In one embodiment, themobile device identifier may be a phone number associated with themobile device 106. In another embodiment, the mobile device identifiermay be a media access control (MAC) address associated with the mobiledevice 106.

The consumer 102 may provide the mobile device identifier via themerchant website in an Internet transaction. In a point-of-saletransaction, the consumer 102 may provide the mobile device identifiervia the point-of-sale terminal, such as by entering of the mobile deviceidentifier on a physical or touch-enabled keypad (which of course themerchant 112 can do for the consumer 102) or via transmission of themobile device identifier from the mobile device 106 to the point-of-saleterminal via near field communication (NFC), or nearly any other form ofinputting or transferring data. In certain instances, the point-of-saleterminal might be another mobile device of the merchant 112,particularly in instances when the merchant 112 is an individualinvolved in a P2P transaction. Methods and systems suitable for thetransmission of information via NFC will be apparent to persons havingskill in the relevant art.

The merchant 112 may receive the mobile device identifier and mayforward the mobile device identifier and any relevant transaction datato an acquirer 114, such as an acquiring bank. The acquirer 114 maysubmit an authorization request to a processing server 116 including thetransaction data and mobile device identifier. The submitting ofauthorization requests for financial transactions will be apparent topersons having skill in the relevant art.

The processing server 116 may include a consumer database 118, which maystore a plurality of wallet data entries. Each wallet data entry mayinclude a mobile device identifier associated with a mobile device andpayment details associated with at least one payment account. Theprocessing server 116 may identify a wallet data entry in the consumerdatabase 118 including the mobile device identifier included in theauthorization request (e.g., associated with the mobile device 106). Theprocessing server 116 may then transmit a selection request to themobile device 106 over the network 120 (e.g., via the mobile networkoperator 110). In some embodiments, the selection request may include aportion of the transaction data, such as for the consumer 102 to use toidentify the financial transaction.

The mobile device 106 may display the received selection request to theconsumer 102 along with a prompt for the consumer 102 to select apayment account to be used to fund the financial transaction. Theconsumer 102 may select a payment account, and the mobile device 106 maysubmit identifying information included in the payment selection data108 to the processing server 116 in response to the selection request.

The processing server 116 may receive the indication of the paymentaccount to be used to fund the financial transaction and may thenidentify payment details associated with the selected payment account inthe wallet data entry associated with the mobile device 106. Theprocessing server 116 may then submit the authorization request to apayment network with the identified payment details included for use infunding the financial transaction. In some embodiments, the processingserver 116 may process the financial transaction. Methods and systemssuitable for processing financial transactions will be apparent topersons having skill in the relevant art. For example, the processingserver 116 may forward the authorization request to the issuer 104,which may identify the payment account and return an authorizationresponse indicating approval or denial of the financial transaction.

The processing server 116 may receive an authorization response from theissuer 104 or the payment network and may forward the authorizationresponse to the acquirer 114 and/or the merchant 112. In someembodiments, the processing server 116 may transmit a notification tothe mobile device 106 indicating approval or denial of the financialtransaction. The merchant 112 may finalize the financial transaction,such as by providing a receipt to the consumer 102 and/or providing thetransacted for products to the consumer 102.

Processing Device

FIG. 2 illustrates an embodiment of the processing server 116 of thesystem 100. It will be apparent to persons having skill in the relevantart that the embodiment of the processing server 116 illustrated in FIG.2 is provided as illustration only and may not be exhaustive to allpossible configurations of the processing server 116 suitable forperforming the functions as discussed herein. For example, the computersystem 800 illustrated in FIG. 8 and discussed in more detail below maybe a suitable configuration of the processing server 116.

The processing server 116 may include a receiving unit 202. Thereceiving unit 202 may be configured to receive an authorization requestfor a financial transaction. The authorization request may include atleast a mobile device identifier, and any other information as will beapparent to persons having skill in the relevant art. The processingserver 116 may also include a transmitting unit 204. The transmittingunit 204 may be configured to transmit, to a mobile device associatedwith the received mobile device identifier (e.g., the mobile device 106)a portion of the transaction data, such as information suitable toenable the consumer 102 to identify the financial transaction asgenuine.

The receiving unit 202 may receive an indication of a payment account tofund the financial transaction from the mobile device 106. Theprocessing server 116 may also include a processing unit 206, which mayidentify a wallet data entry 208 in the consumer database 118 thatincludes the mobile device identifier. The wallet data entry 208 mayalso include payment details associated with at least one paymentaccount. The processing unit 206 may identify the payment accountindicated by the consumer 102 and may identify the associated paymentdetails. The transmitting unit 204 may then transmit an authorizationrequest including the identified payment details to the issuer 104and/or a payment network.

In instances where the processing server 116 may operate as a paymentnetwork, the receiving unit 202 may be further configured to receive anauthorization response from the issuer 104. The transmitting unit 204may then forward the authorization response to the merchant 112 and/orthe acquirer 114. In some embodiments, the transmitting unit 204 mayalso transmit a notification to the mobile device 106 indicatingapproval or denial of the financial transaction.

In one embodiment, the payment details associated with each paymentaccount in each of the wallet data entries 208 may further include amobile personal identification number (PIN). The mobile PIN may be anumber or value associated with the payment account used forauthentication as will be apparent to persons having skill in therelevant art. In such an embodiment, the indication of a selectedpayment account received by the receiving unit 202 may further include aprovided PIN as entered by the consumer 102 upon selection of thepayment account. The processing unit 206 may validate the provided PINusing methods apparent to persons having skill in the relevant art.

If the provided PIN is invalid (e.g., does not correspond to the mobilePIN associated with the payment account or otherwise fails validation),the processing unit 206 may respond to the authorization request bysubmitting an authorization response indicating denial of the financialtransaction. In such an instance, the transaction may be denied withoutproceeding to the issuer 104. In some instances, the processing server116 may transmit a notification to the issuer 104 of the failedvalidation of the PIN for the financial transaction. If, on the otherhand, the provided PIN is valid, the processing server 116 may continuewith the processing of the financial transaction using methods andsystems as will be apparent to persons having skill in the relevant art.

Transaction Processing Flow

FIGS. 3A and 3B illustrate a processing flow for the processing of afinancial transaction using the system 100 of FIG. 1.

In step 302, the consumer 102 may initiate a financial transaction withthe merchant 112. In some embodiments, the financial transaction may bean in-person transaction. In other embodiments, the financialtransaction may be an electronic transaction, such as conducted via theInternet at a website operated by or on behalf of the merchant 112. Instep 304, the merchant 112 may enter transaction data into a transactionsystem, such as by scanning or entering product or service informationinto a point-of-sale system or accepting consumer input of products orservices on the merchant webpage.

In step 306, the merchant 112 may prompt the consumer 102 to providepayment details for the financial transaction. In step 308, the consumer102 may provide a mobile device identifier as a method of payment. Inone embodiment, the consumer 102 may enter the mobile device identifierinto a point-of-sale terminal. In another embodiment, the consumer 102may provide (e.g., orally) the mobile device identifier to an employeeof the merchant 102 for entry into the transaction system. In yetanother embodiment, the mobile device identifier may be transmitted to apoint-of-sale device by the mobile device 106, such as via NFC. Inanother embodiment, the consumer 102 may input the mobile deviceidentifier on the merchant webpage. In an exemplary embodiment, themobile device identifier may be a phone number. When the merchant 112 isanother person (recipient), the consumer's mobile device details can beentered into the recipient's mobile device or other computing device.

In step 310, the merchant 112 (e.g., or the acquirer 114 on behalf ofthe merchant 112) may submit an authorization request for the financialtransaction, wherein the authorization request includes transaction dataand the mobile device identifier. Transaction data may include any datasuitable for the processing of the financial transaction, such as atransaction amount, a transaction time and/or date, merchant details,product details, a loyalty number, an invoice number, a purchase ordernumber, shipping details, etc.

In step 312, the processing server 116 may receive the authorizationrequest. Then, in step 314, the processing server 116 may submit arequest for a selection of payment to the mobile device 106. In someembodiments, the request for a selection of payment may include at leasta portion of the transaction data, such as the transaction time and/ordate, merchant details (e.g., name of the merchant 112), and thetransaction amount. In step 316, the mobile device 106 may prompt (e.g.,via a display unit) the consumer 102 to select a payment account basedon data included in the payment selection data 108.

In step 318, the consumer 102 may select a payment account using aninput unit of the mobile device 106, such as a keyboard, mouse, clickwheel, touch screen, etc. In step 320, the mobile device 106 may receivethe input from the consumer 102 selecting the payment account. Then, themobile device 106 may transmit information indicating the selectedpayment account (e.g., an account identifier, such as the last fourdigits of the account number), to the processing server 116. Theprocessing server 116 may, in step 322, receive the indication of theselected payment account and may identify, in the consumer database 118,a wallet data entry 208 including the mobile device identifier and mayidentify payment details associated with the payment account indicatedby the consumer 102.

In step 324, the processing server 116 may transmit an authorizationrequest including the identified payment details to the issuer 104associated with the payment account indicated by the consumer 102. Theauthorization request may include any additional transaction datasuitable for the authorization of the financial transaction by theissuer 104 as will be apparent to persons having skill in the relevantart. In step 326, the processing server 116 may receive an authorizationresponse from the issuer 104 indicating approval or denial of thefinancial transaction. Then, in step 328, the processing server 116 mayprocess the financial transaction and forward the authorization responseto the merchant 112 (e.g., and/or the acquirer 114). In someembodiments, the processing server 116 may also submit a notification tothe mobile device 106 indicating approval or denial of the financialtransaction, which, in step 330, may be displayed by the display unit ofthe mobile device 106.

In step 332, the merchant 112 may receive the authorization responsefrom the processing server 116 or the acquirer 114. Then, in step 334,the merchant 112 may finalize the financial transaction. In someembodiments, step 334 can involve a merchant 112 going to an ATM toreceive payment in cash, particularly when the merchant 112 is anindividual receiving a P2P payment. The merchant would have to enteridentifying information (e.g., an account number, mobile phone number,or transaction reference number and a PIN or other security check, theselected or designated ATM network or networks at which the payment isavailable, perhaps received as part of the authorization response 332)to initiate the dispensing of cash from the ATM. In some embodiments,finalizing of the financial transaction may include providing thetransacted for products to the consumer 102, which may be received bythe consumer 102 in step 336.

Identification of Payment Details and Processing of FinancialTransactions

FIG. 4 illustrates a method 400 for the identification of paymentdetails by the processing server 116 and the processing of financialtransactions funded by a payment account indicated by the consumer 102via the mobile device 106.

In step 402, the processing server 116 may receive (e.g., via thereceiving unit 202) an authorization request and/or a payment detailsrequest. In step 404, the processing unit 206 may identify if therequest includes a mobile device identifier. If the request does notinclude a mobile device identifier, then the method 400 may proceed tostep 418 to process the financial transaction using traditional systemsand methods apparent to persons having skill in the relevant art. If theprocessing unit 206 identifies a mobile device identifier in therequest, then, in step 406, the transmitting unit 204 may transmit apayment selection request to the mobile device 106. In some instances,the payment selection request may also include transaction data.

In step 408, the receiving unit 202 may receive an indication of apayment account from the mobile device 106 in response to the paymentselection request. Then, in step 410, the processing unit 206 mayidentify a wallet data entry 208 in the consumer database 118 includingthe mobile device identifier. Then, in step 412, the processing unit 206may identify payment details in the wallet data entry 208 associatedwith the payment account indicated as received from the mobile device106.

In step 414, the processing unit 206 may identify if an authorizationrequest is to be submitted (e.g., if the request received in step 402was an authorization request). If an authorization request does not needto be submitted, such as if the request was a request for paymentdetails (e.g., by a payment network, the acquirer 114, the merchant 112,etc.), then, in step 416, the transmitting unit 204 may transmit theidentified payment details in response to the payment details request.

If, in step 414, the processing unit 206 identifies an authorizationrequest is to be submitted, then the method 400 may proceed to step 418to process the financial transaction using traditional methods as willbe apparent to persons having skill in the relevant art. In one suchmethod, the transmitting unit 204 may transmit an authorization requestincluding the payment details to the issuer 104 in step 418. Then, instep 420, the receiving unit 202 may receive an authorization responsefrom the issuer 104 indicating approval or denial of the financialtransaction. In step 422, the transmitting unit 204 may transmit theauthorization response to the acquirer 114 for finalization of thefinancial transaction.

Graphical User Interface

FIGS. 5A-5F illustrate an exemplary graphical user interface of themobile device 106 and a computing device for the conducting of anelectronic financial transaction by the consumer 102 using the mobiledevice 106 for the indication of a payment account used to fund thefinancial transaction. It will be apparent to persons having skill inthe relevant art that the interface illustrated in FIGS. 5A-5F isprovided as an illustration only, and additional interfaces may besuitable. Furthermore, it should be noted that the graphical userinterface illustrated in FIGS. 5A-5F is with respect to an Internettransaction, and that different interfaces may be used for other typesof financial transactions, such as point-of-sale transactions.

FIG. 5A illustrates a web browsing application 502, which may display amerchant webpage 504. The merchant webpage 504 may be part of a merchantwebsite hosted by or on behalf of the merchant 112 for the purchasing ofproducts (e.g., goods or services) by the consumer 102. The consumer 102may navigate to the merchant website and may select one or more productsfor purchase. The consumer 102 may initiate the financial transactionfor the selected products and may be presented with the merchant webpage504 illustrated in FIG. 5A.

The merchant webpage 504 may include product details 506. The productdetails 506 may be a list of information for each product selected forpurchase by the consumer 102, such as a product image, product name,product description, quantity, product cost, color, quality, shippingmethod, etc. The merchant webpage 504 may also include a transactionamount 508. The transaction amount 508 may be the total amount theconsumer 102 must pay in order to receive the selected products.

The merchant webpage 504 may also include a plurality of payment methods510. The payment methods 510 may include one or more methods of paymentaccepted by the merchant 112 for Internet transactions, such as creditcard, wire transfer, gift card, virtual payment account, etc. Theconsumer 102 may select a button indicating payment to be made using themobile device 106. Upon making the indication to pay using the mobiledevice 106, the merchant webpage 504 may display a mobile deviceidentifier field 512 and a submit button 514.

The consumer 102 may enter the mobile device identifier corresponding tothe mobile device 106 to be used for payment into the mobile deviceidentifier field 512. As illustrated in FIG. 5A, the mobile deviceidentifier may be a phone number associated with the mobile device 106.The consumer 102 may then interact with the submit button 514. When theconsumer 102 interacts with the submit button 514, a webserver hostingthe merchant webpage 504 may receive the mobile device identifier andmay transmit a payment details request to the processing server 116including the mobile device identifier and transaction data. Themerchant webpage 504 may then display a waiting notification 516,illustrated in FIG. 5B, which may indicate to the consumer 102 that themerchant webpage 504 is awaiting a response from the processing server116 prior to continuing.

The processing server 116 may, upon receiving the mobile deviceidentifier from the webserver, transmit a payment selection request tothe mobile device 106. In some embodiments, the payment selectionrequest may include at least a portion of the transaction data. Asillustrated in FIG. 5C, the mobile device 106 may display, via a displayunit 518, transaction details 520 for the financial transaction, such asa merchant name and a transaction time and/or date. The display unit 518may also display the product details 506 and the transaction amount 508.The display unit 518 may further display at least one funding source522, such as a plurality of payment accounts based on data included inthe payment selection data 108. As illustrated in FIG. 5C, the at leastone funding source 522 may include two payment card accounts.

The consumer 102 may interact with one of the at least one fundingsources 522 to indicate the corresponding payment account to be used tofund the financial transaction. Then, the display unit 518 may display,as illustrated in FIG. 5D, the indicated payment account 524 and a PINentry field 526. The consumer 102 may enter a PIN associated with theindicated payment account 524 into the PIN entry field 526 in order toauthenticate the consumer 102. The consumer 102 may then interact with asubmit button 528. Upon interaction with the submit button 528, themobile device 106 may transmit information identifying the indicatedpayment account 524 and the entered PIN to the processing server 116. Asillustrated in FIG. 5E, the display unit 518 may then display atransmission notification 530 to notify the consumer 102 thattransmission of the indication of the payment account is being performedby the mobile device 106. It will be apparent to persons having skill inthe relevant art that, in some instances, the graphical user interfaceof the mobile device 106 illustrated in FIGS. 5C-5E may be implanted viaan application program configured to be executed on the mobile device106.

The processing server 116 may, once the indication of the paymentaccount is received, process the financial transaction using methods asdisclosed herein. Once the transaction has been processed, theprocessing server 116 may transmit an authorization response to themerchant 112 and/or the webserver operating the merchant website. Then,as illustrated in FIG. 5F, the merchant website may present aconfirmation webpage 532 to the consumer 102. The confirmation webpage532 may display information to the consumer 102 confirming theprocessing of the financial transaction, such as the transaction details520, the product details 506, the transaction amount 508, and theindicated payment account 524. Additional information suitable fordisplay on the confirmation webpage 532 will be apparent to personshaving skill in the relevant art, such as shipping information, receiptoptions, etc.

Exemplary Method for Processing a Financial Transaction

FIG. 6 illustrates a method 600 for the processing of a financialtransaction by the processing server 116 based on a payment accountindicated by the mobile device 106.

In step 602, a plurality of wallet data entries (e.g., wallet dataentries 208) may be stored in a database (e.g., the consumer database118), wherein each wallet data entry 208 includes at least a mobiledevice identifier and payment details associated with at least onepayment account. In one embodiment, the payment account may be a paymentcard account. In some embodiments, the payment details may include atleast one of: a payment account number, an expiration date, and asecurity code.

In step 604, an authorization request for a financial transaction may bereceived by a receiving device (e.g., the receiving unit 202), whereinthe authorization request includes at least a mobile device identifierand transaction data. In one embodiment, the transaction data mayinclude at least one of: a transaction time and/or date, transactionamount, merchant identifier, product details, shipping details, loyaltynumber, purchase order number, invoice number, and transactionidentifier.

In step 606, at least the transaction data may be transmitted to amobile computing device (e.g., the mobile device 106) associated withthe mobile device identifier. In one embodiment, the mobile deviceidentifier may be a phone number associated with the mobile device 106.In another embodiment, the mobile device identifier may be a mediaaccess control (MAC) address. In step 608, an indication of a paymentaccount for funding of the financial transaction may be received fromthe mobile computing device 106.

In step 610, payment details associated with the indicated paymentaccount may be identified in a wallet data entry 208 of the consumerdatabase 118 including the mobile device identifier included in theauthorization request. In step 612, at least the payment details and thetransaction data may be transmitted to an issuer (e.g., the issuer 104)associated with the indicated payment account. In one embodiment, thepayment details associated with each payment account may include amobile PIN, the receiving indication may further include a provided PIN,and step 612 may be performed only if the provided PIN corresponds tothe mobile PIN included in the payment details associated with theindicated payment account.

In one embodiment, the method 600 may further include receiving, by thereceiving device 202, an authorization response indicating approval ofthe financial transaction, and transmitting, by a transmitting device(e.g., the transmitting unit 204), the authorization response.

Exemplary Method for Identifying Payment Details

FIG. 7 illustrates a method 700 for the identification of paymentdetails by the processing server 116 associated with a payment accountindicated via the mobile device 106.

In step 702, a plurality of wallet data entries (e.g., wallet dataentries 208) may be stored in a database (e.g., the consumer database118), wherein each wallet data entry 208 includes at least a mobiledevice identifier and payment details associated with at least onepayment account. In one embodiment, the payment account may be a paymentcard account. In some embodiments, the payment details may include atleast one of: a payment account number, an expiration date, and asecurity code.

In step 704, a receiving device (e.g., the receiving unit 202) mayreceive a payment information request, wherein the payment informationrequest includes a mobile device identifier. In step 706, a selectionrequest may be transmitted to a mobile computing device (e.g., themobile device 106) associated with the mobile device identifier. In oneembodiment, the mobile device identifier may be a phone numberassociated with the mobile computing device 106. In another embodiment,the mobile device identifier may be a media access control (MAC)address.

In step 708, an indication of a payment account may be received, fromthe mobile computing device 106, in response to the transmittedselection request. In step 710, a specific wallet data entry (e.g., awallet data entry 208) may be identified, in the consumer database 118,where the specific wallet data entry 208 includes the mobile deviceidentifier included in the payment information request.

In step 712, payment details associated with the indicated paymentaccount may be identified in the specific wallet data entry 208. In step714, a transmitting device (e.g., the transmitting unit 204) maytransmit the identified payment details. In one embodiment, the paymentdetails associated with the at least one payment account may eachinclude a mobile PIN, the received indication may further include aprovided PIN, and step 714 may be performed only if the provided PINcorresponds to the mobile PIN included in the payment details associatedwith the indicated payment account.

Computer System Architecture

FIG. 8 illustrates a computer system 800 in which embodiments of thepresent disclosure, or portions thereof, may be implemented ascomputer-readable code. For example, the mobile device 102, processingserver 116, issuer 104, merchant 112, acquirer 114, and mobile networkoperator 110 of FIG. 1 may be implemented in the computer system 800using hardware, software, firmware, non-transitory computer readablemedia having instructions stored thereon, or a combination thereof andmay be implemented in one or more computer systems or other processingsystems. Hardware, software, or any combination thereof may embodymodules and components used to implement the methods of FIGS. 4A, 4B, 6,and 7.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform or a special purpose device. A personhaving ordinary skill in the art may appreciate that embodiments of thedisclosed subject matter can be practiced with various computer systemconfigurations, including multi-core multiprocessor systems,minicomputers, mainframe computers, computers linked or clustered withdistributed functions, as well as pervasive or miniature computers thatmay be embedded into virtually any device. For instance, at least oneprocessor device and a memory may be used to implement the abovedescribed embodiments.

A processor device as discussed herein may be a single processor, aplurality of processors, or combinations thereof. Processor devices mayhave one or more processor “cores.” The terms “computer program medium,”“non-transitory computer readable medium,” and “computer usable medium”as discussed herein are used to generally refer to tangible media suchas a removable storage unit 818, a removable storage unit 822, and ahard disk installed in hard disk drive 812.

Various embodiments of the present disclosure are described in terms ofthis example computer system 800. After reading this description, itwill become apparent to a person skilled in the relevant art how toimplement the present disclosure using other computer systems and/orcomputer architectures. Although operations may be described as asequential process, some of the operations may in fact be performed inparallel, concurrently, and/or in a distributed environment, and withprogram code stored locally or remotely for access by single ormulti-processor machines. In addition, in some embodiments the order ofoperations may be rearranged without departing from the spirit of thedisclosed subject matter.

Processor device 804 may be a special purpose or a general purposeprocessor device. The processor device 804 may be connected to acommunication infrastructure 806, such as a bus, message queue, network,multi-core message-passing scheme, etc. The network may be any networksuitable for performing the functions as disclosed herein and mayinclude a local area network (LAN), a wide area network (WAN), awireless network (e.g., WiFi), a mobile communication network, asatellite network, the Internet, fiber optic, coaxial cable, infrared,radio frequency (RF), or any combination thereof. Other suitable networktypes and configurations will be apparent to persons having skill in therelevant art. The computer system 800 may also include a main memory 808(e.g., random access memory, read-only memory, etc.), and may alsoinclude a secondary memory 810. The secondary memory 810 may include thehard disk drive 812 and a removable storage drive 814, such as a floppydisk drive, a magnetic tape drive, an optical disk drive, a flashmemory, etc.

The removable storage drive 814 may read from and/or write to theremovable storage unit 818 in a well-known manner. The removable storageunit 818 may include a removable storage media that may be read by andwritten to by the removable storage drive 814. For example, if theremovable storage drive 814 is a floppy disk drive, the removablestorage unit 818 may be a floppy disk. In one embodiment, the removablestorage unit 818 may be non-transitory computer readable recordingmedia.

In some embodiments, the secondary memory 810 may include alternativemeans for allowing computer programs or other instructions to be loadedinto the computer system 800, for example, the removable storage unit822 and an interface 820. Examples of such means may include a programcartridge and cartridge interface (e.g., as found in video gamesystems), a removable memory chip (e.g., EEPROM, PROM, etc.) andassociated socket, and other removable storage units 822 and interfaces820 as will be apparent to persons having skill in the relevant art.

Data stored in the computer system 800 (e.g., in the main memory 808and/or the secondary memory 810) may be stored on any type of suitablecomputer readable media, such as optical storage (e.g., a compact disc,digital versatile disc, Blu-ray disc, etc.) or magnetic tape storage(e.g., a hard disk drive). The data may be configured in any type ofsuitable database configuration, such as a relational database, astructured query language (SQL) database, a distributed database, anobject database, etc. Suitable configurations and storage types will beapparent to persons having skill in the relevant art.

The computer system 800 may also include a communications interface 824.The communications interface 824 may be configured to allow software anddata to be transferred between the computer system 800 and externaldevices. Exemplary communications interfaces 824 may include a modem, anetwork interface (e.g., an Ethernet card), a communications port, aPCMCIA slot and card, etc. Software and data transferred via thecommunications interface 824 may be in the form of signals, which may beelectronic, electromagnetic, optical, or other signals as will beapparent to persons having skill in the relevant art. The signals maytravel via a communications path 826, which may be configured to carrythe signals and may be implemented using wire, cable, fiber optics, aphone line, a cellular phone link, a radio frequency link, etc.

Computer program medium and computer usable medium may refer tomemories, such as the main memory 808 and secondary memory 810, whichmay be memory semiconductors (e.g. DRAMs, etc.). These computer programproducts may be means for providing software to the computer system 800.Computer programs (e.g., computer control logic) may be stored in themain memory 808 and/or the secondary memory 810. Computer programs mayalso be received via the communications interface 824. Such computerprograms, when executed, may enable computer system 800 to implement thepresent methods as discussed herein. In particular, the computerprograms, when executed, may enable processor device 804 to implementthe methods illustrated by FIGS. 4A, 4B, 6, and 7, as discussed herein.Accordingly, such computer programs may represent controllers of thecomputer system 800. Where the present disclosure is implemented usingsoftware, the software may be stored in a computer program product andloaded into the computer system 800 using the removable storage drive814, interface 820, and hard disk drive 812, or communications interface824.

Techniques consistent with the present disclosure provide, among otherfeatures, systems and methods for mapping mobile cloud accounts topayment accounts and the processing of financial transactions fundedthereof. While various exemplary embodiments of the disclosed system andmethod have been described above it should be understood that they havebeen presented for purposes of example only, not limitations. It is notexhaustive and does not limit the disclosure to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practicing of the disclosure,without departing from the breadth or scope. For instance, the mobilewallet can include the ability to receive and store coupons or otheroffers, particularly location-based offers based on usage preferences,sharing offers and other information on social media or via SMS ore-mail, enable money transfers, air-time top-ups, purchasing packagessuch as data/voice plans, utility payments, payment services for theunbanked and/or having no credit lines, as will be apparent to thoseskilled in the art.

What is claimed is:
 1. A computer-implemented method for processing afinancial transaction, comprising: storing, in a database of aprocessing server device, a plurality of wallet data entries, whereineach wallet data entry includes at least a mobile device identifier andpayment details associated with at least one payment account; receiving,by a receiving device of the processing server device, an authorizationrequest for a financial transaction from a transaction system of amerchant involved in the financial transaction, wherein theauthorization request includes at least a specific mobile deviceidentifier and transaction data and does not include payment details; inresponse to receiving the authorization request, transmitting, by atransmitting device of the processing server device, over acommunication network, via a mobile network operator (MNO), a selectionrequest including at least the transaction data to a mobile computingdevice associated with the specific mobile device identifier included inthe authorization request, wherein said transmission activates anapplication program installed on the mobile computing device causing themobile computing device to (i) display, on a display thereof, selectiondata including at least one payment account and (ii) promptuser-selection of a payment account from the at least one paymentaccount, wherein payment details associated with the at least onepayment account are not stored on the mobile computing device;receiving, by the receiving device of the processing server device, viathe communication network, an indication of a selected payment accountfor funding of the financial transaction from the mobile computingdevice; identifying, by a processing device of the processing serverdevice, the payment details associated with the indicated selectedpayment account in a wallet data entry stored in the database includingthe mobile device identifier included in the authorization request; andtransmitting, by the transmitting device of the processing serverdevice, at least the payment details associated with the indicatedselected payment account and the transaction data to a payment networkfor approval of the payment transaction.
 2. The method of claim 1,further comprising: receiving, by the receiving device, an authorizationresponse from the payment network indicating approval of the financialtransaction; and transmitting, by the transmitting device, theauthorization response to the merchant.
 3. The method of claim 1,wherein the transaction data includes at least one of: a transactiontime and/or date, transaction amount, merchant identifier, productdetails, shipping details, loyalty number, purchase order number,invoice number, and transaction identifier.
 4. The method of claim 1,wherein the mobile device identifier is a phone number associated withthe associated mobile computing device.
 5. The method of claim 1,wherein the mobile device identifier is a media access control (MAC)address.
 6. The method of claim 1, wherein the transaction data istransmitted to the mobile computing device associated with the mobiledevice identifier included in a short message service (SMS) message. 7.The method of claim 1, wherein the payment account is a payment cardaccount.
 8. The method of claim 1, wherein the payment details includeat least one of: payment account number, expiration date, and securitycode.
 9. The method of claim 1, wherein the payment details associatedwith the at least one payment account each include a mobile personalidentification number (PIN), the received indication further includes aprovided PIN, and the payment details and transaction data aretransmitted to the issuer if the provided PIN corresponds to the mobilePIN included in the payment details associated with the indicatedpayment account.
 10. An electronic system for processing a financialtransaction, comprising: a processing device, of a processing serverdevice; a database device, of the processing server device, configuredto store a plurality of wallet data entries, wherein each wallet dataentry includes at least a mobile device identifier and payment detailsassociated with at least one payment account; a receiving device, of theprocessing server device, configured to receive an authorization requestfor a financial transaction from a transaction system of a merchantinvolved in the financial transaction, wherein the authorization requestincludes at least a specific mobile device identifier and transactiondata and does not include payment details; and a transmitting device, ofthe processing server device, configured to transmit, over acommunication network, via a mobile network operator (MNO), in responseto receiving the authorization request, to a mobile computing deviceassociated with the specific mobile device identifier included in theauthorization request, a selection request including at least thetransaction data, wherein said transmission activates an applicationprogram installed on the mobile computing device causing the mobilecomputing device to (i) display, on a display thereof, selection dataincluding at least one payment account and (ii) prompt user-selection ofa payment account from the at least one payment account, wherein paymentdetails associated with the at least one payment account are not storedon the mobile computing device; wherein the receiving device is furtherconfigured to receive, from the mobile computing device, via thecommunication network, an indication of a selected payment account forfunding of the financial transaction, the processing device isconfigured to identify, in the database, the payment details associatedwith the indicated selected payment account in a wallet data entryincluding the mobile device identifier included in the authorizationrequest, and the transmitting device is further configured to transmit,to a payment network, at least the payment details associated with theindicated selected payment account and the transaction data for approvalof the payment transaction.
 11. The system of claim 10, wherein: thereceiving device is further configured to receive, from the paymentnetwork, an authorization response indicating approval of the financialtransaction; and the transmitting device is further configured totransmit the authorization response to the merchant.
 12. The system ofclaim 10, wherein the transaction data includes at least one of: atransaction time and/or date, transaction amount, merchant identifier,product details, shipping details, loyalty number, purchase ordernumber, invoice number, and transaction identifier.
 13. The system ofclaim 10, wherein the mobile device identifier is a phone numberassociated with the associated mobile computing device.
 14. The systemof claim 10, wherein the mobile device identifier is a media accesscontrol (MAC) address.
 15. The system of claim 10, wherein thetransaction data is transmitted to the mobile computing deviceassociated with the mobile device identifier included in a short messageservice (SMS) message.
 16. The system of claim 10, wherein the paymentaccount is a payment card account.
 17. The system of claim 10, whereinthe payment details include at least one of: payment account number,expiration date, and security code.
 18. The system of claim 10, whereinthe payment details associated with at least one payment account eachinclude a mobile personal identification number (PIN), the receivedindication further includes a provided PIN, and the transmitting deviceis configured to transmit the payment details and transaction data tothe issuer if the provided PIN corresponds to the mobile PIN included inthe payment details associated with the indicated payment account.